Skip to content

Disconnect the WebSocket after an idle period #911

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Mar 18, 2023
Merged

Conversation

shepmaster
Copy link
Member

After deploying the WebSocket reconnection logic, our total connection count slowly grew until nginx stopped being able to handle new connections, leading to a severely degraded experience.

Closing the WebSocket for idle consumers should reduce the concurrent connection count. Eventually we will need to handle re-starting the connection anyway (and potentially only starting it on demand).

After deploying the WebSocket reconnection logic, our total connection
count slowly grew until nginx stopped being able to handle new
connections, leading to a severely degraded experience.

Closing the WebSocket for idle consumers should reduce the concurrent
connection count. Eventually we will need to handle re-starting the
connection anyway (and potentially only starting it on demand).
@shepmaster shepmaster added the maintenance Keeping the wheels turning label Mar 18, 2023
@shepmaster shepmaster merged commit 764833e into main Mar 18, 2023
@shepmaster shepmaster deleted the calm-down-websockets branch March 18, 2023 01:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
maintenance Keeping the wheels turning
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant